…for source-controlled projects

When source control is enabled, the project-root local.settings.json and the
workflow-designtime folder are gitignored, so a fresh clone lacks them and the
design-time host cannot start. Add validateProjectArtifacts to detect and
regenerate these artifacts:

- Scan connections.json, parameters.json and workflows for @appsetting('X')
  references and ensure the root local.settings.json has the baseline schema
  plus placeholder entries for every referenced key (never overwriting values).
- Validate the workflow-designtime folder (host.json + local.settings.json) and
  regenerate it when missing or invalid.

Wired into startDesignTimeApi so artifacts are validated/regenerated before the
host launches. Covered by validateProjectArtifacts.test.ts (incl. golden content
by logic app type, reconstructed from shared constants) and updated
startDesignTimeApi tests.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…h creation path

getLocalSettingsSchema built the root (non-design-time) Values in a different
key order than CreateLogicAppWorkspace.createLocalConfigurationFiles, so a
regenerated local.settings.json was key-for-key reordered versus a freshly
created project (e.g. APP_KIND/FUNCTIONS_WORKER_RUNTIME first instead of
AzureWebJobsStorage first). Reorder the root branch to mirror the creation path
(AzureWebJobsStorage, FUNCTIONS_INPROC_NET8_ENABLED, FUNCTIONS_WORKER_RUNTIME,
APP_KIND, ProjectDirectoryPath, [WORKFLOW_CODEFUL_ENABLED]); design-time order
is unchanged. Add key-order regression tests (toEqual ignores property order).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…esign-time dir

Add a regression test for the codeful branch where workflow-designtime already
exists but its host.json and local.settings.json are invalid (wrong bundle id /
missing required keys). Verifies both artifacts are rewritten to the codeful
baseline (host.json + local.settings.json incl. WORKFLOW_CODEFUL_ENABLED),
closing the gap where only the missing-directory codeful path was covered.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…d projects

The regeneration feature restored the root local.settings.json and the workflow-designtime folder, but never regenerated the project-level host.json. When source control strips this git-ignored file from a fresh clone the function host cannot start.

Add regenerateRootHostFile (mirroring the workspace creation path host.json content) and wire it into validateAndRegenerateProjectArtifacts and promptStartDesignTimeOption. Rename isDesignTimeHostFileValid to isHostFileValid since it now validates both the root and design-time host.json.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Adds output-channel logging at every decision point in the host.json / local.settings.json regeneration flow: which files are checked and whether they exist, whether each file was regenerated or preserved, and how many logic app folders were detected. Crucially logs when zero logic app folders are detected, which happens when host.json is missing (a folder is only recognized as a logic app when host.json exists), explaining why regeneration appears to do nothing in that case.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…r, design-time settings validation, and promptStartDesignTimeOption regeneration

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…er logic app type

Locks current regenerateLocalSettings output for logicApp/customCode/rulesEngine/codeful before refactoring. Documents the known gaps (customCode/rulesEngine undetected at regen time; codeful missing AzureWebJobsFeatureFlags) so upcoming fixes surface as intentional test diffs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…ion and regeneration

Extract getRootLocalSettings(logicAppFolderPath, logicAppType) as the single source of truth for the project-root local.settings.json. Both createLocalConfigurationFiles (fresh project creation) and regenerateLocalSettings (source-control regeneration) now build the file from it, so a regenerated file is key-for-key identical to a freshly created project of the same type.

Regeneration already detects codeful via isCodefulProject, so codeful projects now regenerate with AzureWebJobsFeatureFlags in addition to WORKFLOW_CODEFUL_ENABLED, matching fresh creation. Also drops AzureFunctionsJobHost__extensionBundle__id from the codeful creation path per review feedback (codeful bundle id is not yet published).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…ettings

Add detectLogicAppProjectType, which infers a source-controlled project's ProjectType from its files: codeful via isCodefulProject, and customCode/rulesEngine via a sibling custom-code functions (.csproj) project in the workspace root. regenerateLocalSettings now uses it so customCode and rulesEngine projects regenerate with AzureWebJobsFeatureFlags=EnableMultiLanguageWorker, matching what fresh creation would produce (previously they were treated as plain codeless).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…gn-time discovery mode

isHostFileValid now requires a non-empty extensionBundle.version, and for the
design-time host.json additionally requires the workflow operation discovery host
mode setting. Extract the setting key into a shared constant.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

… directory

ensureDesignTimeDirectory previously used projectPath.includes(designTimeDirectoryName),
which false-positives on siblings such as workflow-designtime-backup. Match on a full
path segment instead so a backup folder gets a nested workflow-designtime directory.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…eneration

Trim inline comments that restated the validateAndRegenerateProjectArtifacts,
regenerateRootHostFile and regenerateLocalSettings docstrings, and remove a
duplicated golden-test comment line. No behavior change.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Rebase onto main picked up upstream's renames of the codeful constant
(workflowCodefulEnabled -> workflowCodefulEnabledKey) and SDK-detection
helper (isCodefulProject -> hasCodefulSdkReference). Update the artifact
regeneration module and its tests to use the current symbol names.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

isLogicAppProject now keys off the workflow-folder signal (codeless workflow.json with a Microsoft.Logic schema, codeful workflow.cs at the project root, or the isCodeful workspace setting) instead of requiring host.json to exist and parse.

host.json is a generic Azure Functions artifact and is commonly gitignored under source control, so a fresh clone can be missing or have a corrupted host.json yet still be a valid logic app project. Keying off the workflow signal lets the extension detect such projects and heal/regenerate host.json, local.settings.json, and workflow-designtime before starting. Also fixes codeful detection to look for workflow.cs at the project root rather than in subfolders.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…roj SDK reference

isLogicAppProject now recognizes a codeful project through hasCodefulSdkReference
(a .NET 8 .csproj referencing Microsoft.Azure.Workflows.Sdk) instead of a hardcoded
workflow.cs filename, so codeful workflows whose C# file is named anything are still
recognized. Adds a statSync default to the fs-extra test mock and unit tests covering
filename-independent codeful detection.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…pProject

The WORKFLOW_CODEFUL_ENABLED workspace setting lives in the gitignored
local.settings.json and adds no detection value alongside the authoritative
.csproj SDK-reference check, so isLogicAppProject no longer consults it. The
isCodeful UI context is now driven by the structural .csproj signal, which also
works for source-controlled projects missing local.settings.json. Adds a test
asserting a folder with only the setting (no .csproj) is not tagged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Renames the golden-content test suites and their baseline objects
(goldenHostJson/goldenRootHostJson -> expectedHostJson/expectedRootHostJson,
'golden ... content by logic app type' -> 'expected ... content by logic app type')
so the intent reads clearly without the golden-test jargon. No behavior change.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>